Mobile based login via wireless credential transfer

ABSTRACT

Systems and methods for mobile-based login via wireless credential transfer are disclosed. In some implementations, a proxy server receives a registration request for a receiver device for accessing a secure resource. The proxy server registers the receiver device in response to the registration request. The proxy server receives, from a transmitter device, information identifying the transmitter device along with authentication credentials for authenticating the receiver device to access the secure resource. The proxy server identifies the receiver device based on the information identifying the transmitter device. The proxy server forwards, to the receiver device, the authentication credentials for authenticating access of the receiver device to the secure resource.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to application Ser. No. 14/069,323, filed onOct. 31, 2013 and titled “MOBILE AUTHENTICATION FOR WEB PAYMENTS USINGSINGLE SIGN ON CREDENTIALS,” application Ser. No. 14/069,080, filed onOct. 31, 2013 and titled “REMOTE AUTHENTICATION USING MOBILE SINGLE SIGNON CREDENTIALS,” and application Ser. No. 14/069,310, filed on Oct. 31,2013 and titled “CONNECTED AUTHENTICATION DEVICE USING MOBILE SINGLESIGN ON CREDENTIALS.” The entire content of the above-identifiedapplications are incorporated herein by reference.

BACKGROUND

Users typically register to access many different online resources, forexample, email service(s), banking service(s), brokerage service(s),utility service(s), social network(s), online store(s), video viewingservice(s), newspapers(s), etc. In order to access an online resource, auser may need to provide login credentials for the online resource. Eachonline resource may have different login credentials associatedtherewith, regardless of whether or not the requirements for setting thelogin credentials are the same or different. Login credentials may beneeded to provide security and to prevent unauthorized persons fromaccessing the online resources. For those online resources whose logincredential requirements are the same, using the same (or even similar)login credentials can thus present an unacceptable security risk, while,on the other hand, remembering multiple different login credentials maybe cumbersome for a user. As the foregoing illustrates, a new approachfor securely providing access to online resource(s) may be desirable.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawing figures depict one or more implementations in accord withthe present teachings, by way of example only, not by way of limitation.In the figures, like reference numerals refer to the same or similarelements.

FIG. 1 illustrates an exemplary system for mobile-based authentication;

FIG. 2 illustrates an exemplary process for mobile-based authentication;

FIGS. 3A-3C illustrate an exemplary process for identifying a receiverdevice configured to receive authentication credentials from atransmitter device;

FIG. 4 is a simplified functional block diagram of a computer that maybe configured to function as the proxy server shown in FIG. 1; and

FIG. 5 is a simplified functional block diagram of a personal computeror other work station or terminal device.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth by way of examples in order to provide a thorough understanding ofthe relevant teachings. However, it should be apparent that the presentteachings may be practiced without such details. In other instances,well known methods, procedures, components, and/or circuitry have beendescribed at a relatively high-level, without detail, in order to avoidunnecessarily obscuring aspects of the present teachings.

As set forth above, users oftentimes create login credentials (e.g.,usernames and passwords) for accessing multiple different web orapplication-based resources. However, users may have difficultyremembering or accessing their login credentials, requiring atime-consuming resetting of the login credentials. However, a usertypically carries a mobile device (e.g., a mobile phone) which isoftentimes on the user's person and accessible to the user. The mobiledevice may be used as an authentication source, as the mobile device maybe a trusted device with the user.

In some aspects, the subject technology provides techniques foraccessing online resources using a mobile device. The mobile device(e.g., a transmitter device) may have an application installed on thedevice, which allows the memory of the mobile device to serve as arepository for the information or credentials which may be transmittedto a receiver device. The mobile device stores credential(s) of a userfor accessing online resource(s). The credential(s) may includeusername(s), passwords(s), payment account information, shipping addressinformation, etc. The receiver device may be any computer including aweb browser or another application for accessing the online resource(s).For example, the receiver device may be a laptop or desktop computer ofthe user that includes a web browser (e.g., Internet Explorer®) or thereceiver device may be a tablet computer or a mobile phone that includesan application for accessing online resource(s), for example, an onlinebanking application or a social networking application. The receiverdevice may lack a wired or short-range radio connection to thetransmitter device. However, oftentimes, when the user attempts toaccess an online resource using the receiver device, both the user andthe transmitter device are proximate to the receiver device and can beused for authenticating access of the receiver device to the onlineresource.

The receiver device may have a service running in the background, suchas a Java applet. Using the service, the receiver device may registeritself as a listener with a hosted forwarding proxy server. The proxyserver is an online server that may connect to the transmitter deviceand the receiver device using one or more of a wired network, a wirelesslocal area network, or a wireless wide area network. In operation, theproxy server receives a registration of one or more receiver devices foraccessing information (e.g., credential(s) for accessing onlineresource(s)) via the proxy server. For example, the user may registerhis/her office desktop computer, home laptop computer, home desktopcomputer, and tablet computer to access information via the proxyserver. The proxy server receives encrypted information (e.g., encryptedcredentials for accessing online resource(s)) from the transmitterdevice for forwarding to the receiver device. For example, the user maydesire to access a social networking service, which requires logincredentials, from his/her home desktop computer (the first receivercomputer) and may transmit the login credentials for accessing thesocial networking service to the home desktop computer from his/hermobile phone. The proxy server transmitting the login credentials fromthe mobile phone to the desktop computer may link or pair the mobilephone and the desktop computer based on the mobile phone and the desktopcomputer being geographically proximate to one another (e.g., within 15meters of one another), being connected to the same WiFi network, orbeing associated with the same user account, stored at the proxy server.

When the user is ready to transmit the information or credential to thereceiver device in proximity to the user, the user may initiate atransfer from the mobile application in the mobile phone. The mobileapplication may first authenticate itself with the proxy server using aunique user identifier that identifies the user and/or the mobiledevice. The unique identifier may include, for example, a username or aMobile Directory Number (MDN).

In one implementation, the proxy server identifies the receiver devicefrom among the plurality registered receiver devices based on thereceiver device being proximate to the transmitter device. For example,the user may be sitting at the desktop computer and the mobile phone maybe on the table proximate to the desktop computer. The proxy serverforwards the encrypted information (e.g., the login credentials foraccessing the social networking service) from the proxy server to thereceiver device. As a result, the receiver device is able to access theonline resource (e.g., log in to the social networking service). Inanother implementation, the proxy server identifies the receiver devicebased on the unique identifier of the receiver device being previouslyassociated with the unique identifier of the mobile device. Once themobile device and the receiver device are paired together, as an addedsecurity, the mobile and/or the receiver device may also be presented achallenge to ensure that both devices should be paired. The challengemay include any type of challenge, for example, a pin-based challenge, apattern challenge, a movement-based challenge, etc. Once the receiverdevice has been identified and authenticated using the above steps, themobile device may send the information or credential to the receiverdevice over an encrypted channel. The communication medium may beencrypted using a shared secret key, which may be commonly developed bythe application and background service developer and preinstalled intoboth pieces of software.

Once the information has been transmitted to the receiver device,depending on the type of information transmitted, the receiver devicemay then choose how to proceed. For example, if the mobile device hastransmitted login credentials for a website, upon receipt, thebackground service of the receiver device may then attempt to use webbrowser auto-fill capability to insert those credentials into theappropriate website with which the user was attempting to authenticate.This method can be extended to sending any kind of information byextending the mobile application to provide different “destinationtypes” and programming the background service of the non-mobile deviceto accept and have access to those various destinations once theinformation is received.

Reference now is made in detail to the examples illustrated in theaccompanying drawings and discussed below. FIG. 1 illustrates anexemplary system 100 for mobile-based authentication. As shown, thesystem 100 includes computing devices such as, for example, a desktopcomputer 110 and a laptop computer 120. The system 100 also includes aproxy server 130 and a mobile device 140. While two computing devices110 and 120 are illustrated, the subject technology may be implementedwith any number of computing devices, which may include a desktopcomputer, a laptop computer, a tablet computer, a mobile phone, apersonal digital assistant (PDA), a digital music player, a smart watch,etc. Also, while the mobile device 140 is illustrated as being a mobilephone, in some cases, the mobile device 140 may be a tablet computer, apersonal digital assistant (PDA), a digital music player, a smart watch,a key fob including one or more processors, a network interface, and amemory, etc. The mobile device 140, the laptop computer 120, and thedesktop computer 110 may be end-user computing devices which may be usedby end-users (e.g., consumers or customers) to access the Internet,write paper(s), play game(s), make telephone call(s), etc.

In one implementation, the computing device(s) 110 and 120 register aslisteners with the proxy server 130 to be able to receive authenticationcredentials from mobile devices, including the mobile device 140 (Step101). To this end, the computing device(s) 110 and 120 may have aconnection service 115 running in the background, for example, a Javaapplet, which may register itself as a listener with the proxy server130. Similarly, the mobile device 140 may have a credential storageapplication 145 installed on the mobile device 140, serving as arepository for the information or credentials which may be transmittedto one of the computing devices 110 or 120.

As described more fully below, when a user is ready to transmit theinformation or credential wirelessly from the mobile device 140 to acomputing device 110 or 120, the user may initiate a transfer from theapplication on the mobile device 140. The application may authenticateitself with the proxy using a unique user identifier (e.g., a usernameor MDN) and sends authentication credentials to the proxy server 130(Step 102). The proxy server 130 determines to which computing device(e.g., desktop computer 110 or laptop 120) the user is attempting totransmit authentication credentials from the mobile device 140, andforwards the authentication credentials from the mobile device 140 tothe computing device 110 or 120 via the established link (Step 103). Thedetermination to which computing device the user is attempting totransmit the authentication credentials may be made based on ageographic proximity of the mobile device 140 to the computing device orbased on a stored pairing, at the proxy server 130, of the mobile device140 and the computing device. After receiving the authenticationcredentials, the computing device 120 may connect to the secure onlineresource 125. The proxy server 130 may match the computing devices 110and 120 with the mobile device 140 based on unique identificationsassociated with the computing devices 110 and 120 and the mobile device140. Alternatively or additionally, the proxy server 130 may match thecomputing devices 110 and 120 with the mobile device 140 based onlocation information associated with the computing devices 110 and 120and the mobile device 140. The proxy server 130 may receive from one ormore computing devices 110 and 120 a geographic location of thecomputing device and receive a geographic location of the mobile device140 from the mobile device 140. The proxy server 130 then determines towhich computing device the user is attempting to transfer thecredentials based on a distance between the geographic locations betweenthe mobile device and the computing device being less than a thresholddistance (e.g., 2 meters, 5 meters, 10 meters, or 100 meters). Thethreshold distance may be set based on an exactness of the geographiclocation of the computing device 110/120, an exactness of the geographiclocation of the mobile device, and a typical distance between a user'smobile phone and laptop or desktop computer when the user is accessingthe laptop or desktop computer. The threshold distance may be a defaultdistance that is set automatically by the network or may be set manuallyby the user such that any computing device-mobile device combinationhaving a geographic separation greater than the threshold distance isnot considered. The computing device(s) and the mobile device 140 maydetermine their geographic locations based on one or more of a globalpositioning system (GPS) signal, a WiFi signal, a cellular signal, or anIP address, for example, using triangulation of GPS or cellular signals,assisted GPS, a data repository (e.g., provided by Google® Corporationof Mountain View, Calif.) for converting WiFi signal(s) into geographiclocation(s), or a data repository for converting IP addresses intogeographic locations. If assisted GPS is used, the threshold time or thetime for processing the connection request may be increased, due to theslower speed of assisted GPS technology. As an added security, after themobile device 140 and the computing device 110/120 are identified by theproxy server 130, the mobile device 140 and/or computing device 110 or120 may also be presented a challenge to ensure that both devices arecorrectly paired. The challenge may include any type of challenge, forexample, a pin-based challenge, a pattern challenge, a movement-basedchallenge, etc. Both devices may be correctly paired, for example, ifboth devices are within the proximity of the authorized user oraccessible to the authorized user. A device may within the proximity ofthe authorized user if the user may access the device with his/her hand,for example, if the device is in the user's purse or pocket or on atable adjacent to the user. A device may be accessible to the authorizeduser if the user is able to access the device. For example, if the useris able to turn on the device, unlock the device, and access software onthe device. For example, the authorized user may be within the proximityof the mobile phone 140 and may not be within the proximity of a remotecomputing device 110 or 120. The user may use an additional computer,different from the remote computing device, to connect to the remotecomputing device 110 or 120 via a virtual private network (VPN), whileboth the mobile phone 140 and the remote computing device 110 or 120 areaccessible to the user.

Once the computing device 110 or 120 has been identified and pairedusing the above steps, the mobile device 140 may then send theinformation or credential to the computing device 110 or 120 over anencrypted channel via the proxy server 130. The encrypted channelcorresponds to the data transmission path from the mobile device 140 tothe computing device 110/120 via the proxy server 130 and is set up uponpairing of the mobile device with the computing device 110/120. Thecommunication medium may be encrypted using a shared secret key whichmay, in some cases, be commonly developed by the application andbackground service developer and preinstalled into both pieces ofsoftware. Once the information has been transmitted to the computingdevice 110 or 120, depending on the type of information transmitted, thecomputing device 110 or 120 may locally determine how to use thetransmitted information. For example, if the mobile device 140 hastransmitted login credentials for a website or an application, uponreceipt, the background service of the computing device 110 or 120 mayattempt to use web browser's auto fill capability to insert thosecredentials into the password input or other credential entry area ofthe appropriate website or application that the user is attempting tosecurely access via the computing device 110 or 120. These techniquesmay be extended to sending any kind of information by extending theapplication of the mobile device 140 to provide different “destinationtypes” and programming the background service of the computing device110 or 120 to accept and have access to those various destinations oncethe information is received. For example, if the computing device110/120 is attempting to access an online store, the mobile device 140may transmit payment information (e.g., credit card number) and shippinginformation (e.g., shipping address) to the computing device 110/120 toexpedite entry of such information. Alternatively, if the user isattempting to fill out a web form (e.g., an employment application or anapplication for a new bank account) at the computing device 110/120, themobile device may transmit information about the user, stored at themobile device (e.g., the user's name, address, telephone number, etc.),for filling out the web form.

According to some implementations, the mobile device 140 transmits, tothe computing device 110 or 120, via the proxy server 130,authentication credentials for authenticating access of the computingdevice 110 or 120 to a secure resource. For example, the user may storehis/her login information to an online banking service at the mobiledevice 140 via the application of the mobile device 140. While at theairport, the user may remember that he/she needs to pay a bill, but notremember his/her password for online banking. In order to access his/heronline banking service, the user may access a desktop computer (e.g.,desktop computer 110) at a kiosk at the airport and may have his/hermobile device 140 transmit the login credentials for the online bankingservice to the desktop computer via the proxy server 130.Advantageously, the user may be permitted to securely access the onlinebanking service while securely identifying him/herself (e.g., bypossessing the mobile device 140) and without needing to rememberhis/her password. To protect the user's privacy, in some cases, theuser's geographic location may not be transmitted to thewebsite/application the user is accessing. Alternatively, withappropriate permission from the user, the geographic location may betransmitted to the website/application, and the website/application mayanalyze the information for statistical purposes (e.g., a socialnetworking service may wish to determine what percentage of its usersaccess the social networking service from locations in New York City.)

FIG. 2 illustrates an exemplary process 200 for mobile-basedauthentication. The process 200 begins at step 210, where a proxy server(e.g., proxy server 130) receives a registration request for a receiverdevice (e.g., one of the computing devices 110 or 120) for accessing asecure resource (e.g., logging into an online banking service, a socialnetworking service, an online store, etc.). The registration request maybe received via any network, for example, the Internet, a wirelessnetwork, a wired network, a local area network, or a wide area network.For example, a user may register his/her personal computer as a receiverdevice to be able to access secure resource(s) using the personalcomputing device. Alternatively, a computing device used by multipledifferent users (e.g., an Internet kiosk at an airport or Internet café)may be registered to receive login credentials from mobile phone(s) ofmany different user(s). The registration request may include geographiclocation information of the receiver device. When registered with theproxy server, a receiver device may not be associated with a specificuser or a specific mobile device. Alternatively, the receiver device maybe associated with a specific user or a specific receiver deviceidentified in the registration request.

In step 220, in response to the registration request, the proxy serverregisters the receiver device in response to the registration request.The registration may include storing, at the proxy server, an identifierof the receiver device. The identifier may include a serial numberand/or location information associated with the receiver device. Theregistration may also include storing, at the receiver device, a service(e.g., a software service) for communicating with the proxy server andallowing the proxy server to provide information (e.g., logincredentials) to application(s) (e.g., a web browser) that provide accessto secure resources.

In step 230, the proxy server receives, from a transmitter device (e.g.,mobile device 140), information identifying the transmitter device alongwith authentication credentials for authenticating the receiver deviceto access the secure resource. The information identifying thetransmitter device may include a username or a MDN. The information mayalso include location information associated with the transmitterdevice. The secure resource may be a web-based resource and theauthentication credentials may include a username and a password foraccessing the web-based resource. The transmitter device may storemultiple credentials for accessing multiple web-based resourcesassociated with a user, for example, credentials for accessing theuser's web-based email(s), social networking service(s), online bankingservice(s), online store(s), etc. The transmitter device and thereceiver device may be end-user computing devices which may be used byend-users (e.g., consumers or customers) to access the Internet, writepaper(s), play game(s), make telephone call(s), etc.

In step 240, in response to receiving the information identifying thetransmitter device, the proxy server identifies the receiver devicebased on information identifying the transmitter device. The proxyserver may receive registration information from a plurality of receiverdevices. Similarly, the proxy server may receive identifying andcredential information from a plurality of transmitter devices. To thisend, the proxy server may match the corresponding receiver andtransmitter devices to ensure that the credentials are forwarded fromthe transmitter device to a correct receiver device.

In one implementation, the proxy server may utilize location informationof the receiver device and the transmitter device to pair the receiverand the transmitter device. The transmitter device may transmitinformation to the proxy server upon being accelerated at anacceleration corresponding to selecting a button while running aspecific application for communicating with the proxy server. Thereceiver device may transmit information to the proxy server upon aselection of a button (e.g., a space bar) thereon while running anapplication (e.g., displaying a webpage via a web browser) with thereceiver device. The user may simultaneously, and while the transmitterdevice and the receiver device are at the same geographic location,indicate that he/she wishes to transmit information from the transmitterdevice to the receiver device by selecting the button on the receiverdevice with the transmitter device (e.g., pressing a spacebar of akeyboard of a laptop or desktop computer with a mobile phone). Inresponse, location information from the receiver device and thetransmitter device, which are separated by a threshold distance (e.g., 5meters, 10 meters, etc.) may be transmitted to the proxy server. Thisinformation can be used to pair the transmitter device and the receiverdevice.

In another implementation, instead or in addition to using the locationinformation, the proxy server may use the time arrival signals from thereceiver device and the transmitter device to pair the receiver deviceand the transmitter device. In keeping with the previous example, theuser may simultaneously, and while the transmitter device and thereceiver device are at the same geographic location, indicate thathe/she wishes to transmit information from the transmitter device to thereceiver device by selecting the button on the receiver device with thetransmitter device (e.g., pressing a spacebar of a keyboard of a laptopor desktop computer with a mobile phone). In response, signals from thetransmitter device and the receiver device, which are separated by athreshold time (e.g., 0.5 seconds, 1 second, 2 seconds, 5 seconds, etc.)may be transmitted to the proxy server. The proxy server may use thisinformation to pair the receiver device and the transmitter device. Thethreshold time may be determined based on a processing speed of thetransmitter device, a processing speed of the receiver device, a networkspeed, etc. The threshold time may be a default time that is setautomatically on the network or may be set manually by the user suchthat signals from the transmitter device and the receiver devicearriving at a time greater than the threshold time are either nottransmitted to the proxy server or are not associated with each other.

In yet another implementation, the proxy server may use priorregistration information to pair the transmitter device and the receiverdevice. For example, the proxy server may be a server of a telephonecompany. The user may register, with the telephone company, computingdevice(s) (e.g., receiver devices) authorized to access paymentinformation via the user's mobile phone (e.g., transmitter device). Thecomputing device(s) may be identified based on cookies stored at thecomputing device(s) or based on identifier(s) of the computing device(s)stored at the proxy server.

In some cases, the receiver device may not have been associated witheither the transmitter device or the user of the transmitter devicepreviously as such using the prior registration implementation may notbe possible. For example, the receiver device may be an Internet kioskin an airport or a lobby of a corporation that the user is using for thefirst time in his/her life. In this scenario, to identify the receiverdevice from among multiple receiver devices registered with the proxyserver, location information may be used. As noted above, the proxyserver may receive the geographic location(s) of the transmitter deviceand the receiver device and pair them based on the receiver device beingless than a threshold distance (e.g., 10 meters, 20 meters, etc.) awayfrom the transmitter device. The proxy server may identify the receiverdevice based on the receiver device being proximate to the transmitterdevice, for example, as described in greater detail below in conjunctionwith FIGS. 3A-3C.

The proxy server may also transmit to the receiver device a verificationcode and receive, at the transmitter device, a user input correspondingto the verification code. Alternatively, the proxy server may transmitto the transmitter device a verification code and receive, at thereceiver device, a user input corresponding to the verification code.The verification code may provide additional security, proving that theuser requesting the information transfer has access to both thetransmitter device and the receiver device at the time of theinformation transfer.

Upon successful pairing of the transmitter device and the receiverdevice, in step 250, the proxy server forwards, to the receiver device,the authentication credentials for authenticating access of the receiverdevice to the secure resource. The receiver device may then access thesecure resource using the authentication credentials. For example, ifthe authentication credentials are for logging into a social networkingservice, the receiver device may log into the social networking service(e.g., via a web browser or a special purpose application for accessingthe social networking service) using the authentication credentials.After step 250, the process 200 ends.

FIGS. 3A-3C illustrate an exemplary process 300 for identifying areceiver device to receive authentication credentials from a transmitterdevice. As shown in FIG. 3A, the process 300 begins at step 310, where aproxy server (e.g., proxy server 130) receives, from a transmitterdevice (e.g., mobile device 140) a geographic location of thetransmitter device. The transmitter device may determine its geographiclocation based one or more GPS, WiFi, cellular, or IP address signalsaccessible to the transmitter device. The transmitter device may provideits geographic location to the proxy server together with a request totransmit data via the proxy server or in response to a prompt from theproxy server.

In step 320, the proxy server receives, from plural receiver devices(e.g., computing devices 110 and 120 of FIG. 1), a geographic locationof each receiver device in the plural receiver devices. The pluralreceiver devices may include all of the receiver devices registered withthe proxy server, receiver devices registered with the proxy server thatare attempting to receive data via the proxy server, or receiver devicesregistered with the proxy server associated with the same account as thetransmitter device.

In step 330, upon receiving the geographic locations of the transmitterdevice and the receiver devices, the proxy server determines whetherzero, a single, or multiple receiver devices from among the pluralreceiver devices have a distance to the transmitter device less than athreshold distance (e.g., 2 meters, 5 meters, or 10 meters). If zeroreceiver devices have a distance to the transmitter device less than thethreshold distance, the process 300 continues to step 340. If onereceiver device has a distance to the transmitter device less than thethreshold distance, the process 300 continues to step 350. If multiplereceiver devices have a distance to the transmitter device less than thethreshold distance, the process 300 continues to either step 360B ofFIG. 3B or step 360C of FIG. 3C, depending on the programming of theproxy server.

In step 340, if zero receiver devices have a distance to the transmitterdevice less than the threshold distance, the proxy server reports anerror in identifying the receiver device. The error may be reported tothe transmitting device. In most situations, a user requesting totransmit authentication credentials from a transmitter device (e.g.,mobile device) to a receiver device (e.g., computing device accessing awebpage) has both the transmitter device and the receiver device athis/her location (e.g., in front of him/herself, in his/her office, inhis/her office, at a café, etc.). Thus, the transmitter device and thereceiver device may, in some cases, be closer to one another than thethreshold distance. After step 340, the process 300 ends.

In step 350, if one receiver device has a distance to the transmitterdevice less than the threshold distance, the proxy server identifies thesingle receiver device as the receiver device to receive theauthentication credentials from the transmitter device. After step 350,the process 300 ends.

In step 360B of FIG. 3B, if multiple receiver devices have a distance tothe transmitter device less than the threshold distance, the proxyserver transmits, to the transmitter device a verification code andperhaps instructions for the user to enter the verification code intothe user's receiver device. The verification code may include a numericpin, a text keyword, a mouse movement, etc.

In step 370B, the proxy server receives, from one of the receiverdevices from among the multiple receiver devices, a user inputcorresponding to the verification code. For example, the user may typethe pin or the keyword into the receiver device or move the mouse of thereceiver device according to the mouse movement in the verificationcode. The user may be provided an interface (e.g., an input box) toenter the verification code at the receiver device. In the event of anincorrect entry or a timeout, the user may be notified that the pairingof the transmitter device and the receiver device was unsuccessful. Theuser may be given the opportunity to reattempt pairing or to access theonline resource using another technique (e.g., manual entry of logincredentials).

In step 380B, the proxy server identifies the one of the receiverdevices as the receiver device to receive the authentication credentialsfrom the transmitter device. After step 380B, the process 300 ends.

In step 360C of FIG. 3C, if multiple receiver devices have a distance tothe transmitter device less than the threshold distance, the proxyserver transmits, to each of the multiple receiver devices, averification code uniquely associated with a corresponding one of themultiple receiver devices and perhaps instructions for the user to enterthe verification code into the user's transmitter device. Each of themultiple receiver devices receives its own unique verification codewhich may include, for example, a numeric pin, a text keyword, a patternto draw on a touchscreen of the transmitter device, a movement of thetransmitter device, an image, an audio signal, etc.

In step 370C, the proxy server receives, from the transmitter device, auser input corresponding to a verification code corresponding to aspecific one of the multiple receiver devices. For example, the user mayenter the numeric pin, enter the text keyword, draw the pattern on thetouchscreen of the transmitter device, move the transmitter deviceaccording to the movement in the verification code corresponding to thespecific one of the multiple receiver devices, take a photograph, usinga camera of the transmitter device, of the image in the verificationcode, displayed on the screen of the specific one of the multiplereceiver devices, with the transmitter device, record the audio signal,using a microphone of the transmitter device, from the specific one ofthe multiple receiver devices with the transmitter device, etc. Taking aphotograph, using the transmitter device, of an image displayed at thereceiver device, or recording audio, using the transmitter device, ofsounds played at the receiver device verifies that the transmitterdevice and the receiver device are proximate (e.g., within a visibilityor hearing range) to one another, as a transmitter device cannot take aphotograph or record audio from a remote receiver device. The user maybe provided an interface (e.g., an input box) to enter the verificationcode at the transmitter device. In the event of an incorrect entry or atimeout, the user may be notified that the pairing of the transmitterdevice and the receiver device was unsuccessful. The user may be giventhe opportunity to reattempt pairing or to access the online resourceusing another technique (e.g., manual entry of login credentials).

If a photograph is used, the proxy server may compare the image that wastransmitted to the receiver devices with the photograph that wasreceived from the transmitter device. If the photograph is similar tothe image (e.g., a Hamming Distance or Sequence Alignment valueindicates that the photograph is similar to the image), the transmitterdevice may be paired with the receiver device. Otherwise, an errormessage may be transmitted to the transmitter device or the receiverdevice indicating that the devices were not paired.

If an audio signal is used, the proxy server may compare the audiosignal that was transmitted to the receiver devices with the soundrecording that was received from the transmitter device. If the audiosignal is similar to the sound recording (e.g., a Hamming Distance orSequence Alignment value indicates that the audio signal is similar tothe sound recording), the transmitter device may be paired with thereceiver device. Otherwise, an error message may be transmitted to thetransmitter device or the receiver device indicating that the deviceswere not paired.

In step 380C, the proxy server identifies the specific one of themultiple receiver devices as the receiver device to receive theauthentication credentials from the transmitter device. After step 380C,the process 300 ends.

According to some implementations, a laptop or desktop computer accessesa website and requests authentication information from the server. Inresponse, the server identifies a corresponding mobile device andrequests credential information from the mobile device using eitherprior registration information, stored at the server, associating thelaptop or desktop computer with the mobile device or using locationinformation indicating that the laptop or desktop computer and themobile device are within a threshold distance (e.g., 5 meters or 10meters) of one another.

According to some implementations, a laptop or desktop computer accessesa website and requests authentication information from the server. Atsubstantially the same time (e.g., within 2 seconds, 5 seconds, 10seconds, etc.), the server also receives identifying information fromthe mobile device and uses the identifying information to match themobile device to the laptop or desktop computer. In some aspects, theidentifying information includes a mobile directory number (MDN) and thematching is based on prior registration information. In some aspects,the identifying information includes geographic location information andthe matching is based on the geographic location information.

FIGS. 4 and 5 provide functional block diagram illustrations of generalpurpose computer hardware platforms. FIG. 4 illustrates a network orhost computer platform, as may typically be used to implement a server.FIG. 5 depicts a computer with user interface elements, as may be usedto implement a personal computer or other type of work station orterminal device, although the computer of FIG. 5 may also act as aserver if appropriately programmed. It is believed that the generalstructure and general operation of such equipment as shown in FIGS. 4and 5 should be self-explanatory from the high-level illustrations.

A server, for example, includes a data communication interface forpacket data communication. The server also includes a central processingunit (CPU), in the form of one or more processors, for executing programinstructions. The server platform typically includes an internalcommunication bus, program storage and data storage for various datafiles to be processed and/or communicated by the server, although theserver often receives programming and data via network communications.The hardware elements, operating systems and programming languages ofsuch servers are conventional in nature. Of course, the server functionsmay be implemented in a distributed fashion on a number of similarplatforms, to distribute the processing load.

A computer type user terminal device, such as a PC or tablet computer,similarly includes a data communication interface CPU, main memory andone or more mass storage devices for storing user data and the variousexecutable programs (see FIG. 5). A mobile device type user terminal mayinclude similar elements, but will typically use smaller components thatalso require less power, to facilitate implementation in a portable formfactor. The various types of user terminal devices will also includevarious user input and output elements. A computer, for example, mayinclude a keyboard and a cursor control/selection device such as amouse, trackball, joystick or touchpad; and a display for visualoutputs. A microphone and speaker enable audio input and output. Somesmartphones include similar but smaller input and output elements.Tablets and other types of smartphones utilize touch sensitive displayscreens, instead of separate keyboard and cursor control elements. Thehardware elements, operating systems and programming languages of suchuser terminal devices also are conventional in nature.

Hence, examples of the methods of managing information about contenttransmission outlined above may be embodied in programming. Programaspects of the technology may be thought of as “products” or “articlesof manufacture” typically in the form of executable code and/orassociated data that is carried on or embodied in a type of machinereadable medium. “Storage” type media include any or all of the tangiblememory of the computers, processors or the like, or associated modulesthereof, such as various semiconductor memories, tape drives, diskdrives and the like, which may provide non-transitory storage at anytime for the software programming. All or portions of the software mayat times be communicated through the Internet or various othertelecommunication networks. Such communications, for example, may enableloading of the software from one computer or processor into another.Thus, another type of media that may bear the software elements includesoptical, electrical and electromagnetic waves, such as used acrossphysical interfaces between local devices, through wired and opticallandline networks and over various air-links. The physical elements thatcarry such waves, such as wired or wireless links, optical links or thelike, also may be considered as media bearing the software. As usedherein, unless restricted to non-transitory, tangible “storage” media,terms such as computer or machine “readable medium” refer to any mediumthat participates in providing instructions to a processor forexecution.

Hence, a machine readable medium may take many forms, including but notlimited to, a tangible storage medium, a carrier wave medium or physicaltransmission medium. Non-volatile storage media include, for example,optical or magnetic disks, such as any of the storage devices in anycomputer(s) or the like, such as may be used to implement theapplication(s) 150, etc. shown in the drawings. Volatile storage mediainclude dynamic memory, such as main memory of such a computer platform.Tangible transmission media include coaxial cables; copper wire andfiber optics, including the wires that comprise a bus within a computersystem. Carrier-wave transmission media may take the form of electric orelectromagnetic signals, or acoustic or light waves such as thosegenerated during radio frequency (RF) and infrared (IR) datacommunications. Common forms of computer-readable media thereforeinclude for example: a floppy disk, a flexible disk, hard disk, magnetictape, any other magnetic medium, a Blu-ray disc read-only memory(BD-ROM), CD-ROM, DVD or DVD-ROM, any other optical medium, punch cardspaper tape, any other physical storage medium with patterns of holes, aRAM, a PROM and EPROM, a FLASH-EPROM, any other memory chip orcartridge, a carrier wave transporting data or instructions, cables orlinks transporting such a carrier wave, or any other medium from which acomputer may read programming code and/or data. Many of these forms ofcomputer readable media may be involved in carrying one or moresequences of one or more instructions to a processor for execution.

These general and specific aspects may be implemented using a system, amethod, a computer program, a computer readable medium, or an apparatusor any combination of systems, methods, computer programs, computerreadable mediums, and/or apparatuses

While the foregoing has described what are considered to be the bestmode and/or other examples, it is understood that various modificationsmay be made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that the teachings may beapplied in numerous applications, only some of which have been describedherein. It is intended by the following claims to claim any and allapplications, modifications and variations that fall within the truescope of the present teachings.

Unless otherwise stated, all measurements, values, ratings, positions,magnitudes, sizes, and other specifications that are set forth in thisspecification, including in the claims that follow, are approximate, notexact. They are intended to have a reasonable range that is consistentwith the functions to which they relate and with what is customary inthe art to which they pertain.

The scope of protection is limited solely by the claims that now follow.That scope is intended and should be interpreted to be as broad as isconsistent with the ordinary meaning of the language that is used in theclaims when interpreted in light of this specification and theprosecution history that follows and to encompass all structural andfunctional equivalents. Notwithstanding, none of the claims are intendedto embrace subject matter that fails to satisfy the requirement ofSections 101, 102, or 103 of the Patent Act, nor should they beinterpreted in such a way. Any unintended embracement of such subjectmatter is hereby disclaimed.

Except as stated immediately above, nothing that has been stated orillustrated is intended or should be interpreted to cause a dedicationof any component, step, feature, object, benefit, advantage, orequivalent to the public, regardless of whether it is or is not recitedin the claims.

It will be understood that the terms and expressions used herein havethe ordinary meaning as is accorded to such terms and expressions withrespect to their corresponding respective areas of inquiry and studyexcept where specific meanings have otherwise been set forth herein.Relational terms such as first and second and the like may be usedsolely to distinguish one entity or action from another withoutnecessarily requiring or implying any actual such relationship or orderbetween such entities or actions. The terms “comprises,” “comprising,”or any other variation thereof, are intended to cover a non-exclusiveinclusion, such that a process, method, article, or apparatus thatcomprises a list of elements does not include only those elements butmay include other elements not expressly listed or inherent to suchprocess, method, article, or apparatus. An element proceeded by “a” or“an” does not, without further constraints, preclude the existence ofadditional identical elements in the process, method, article, orapparatus that comprises the element.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various embodiments for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separately claimed subject matter.

What is claimed is:
 1. A method comprising: receiving, at a proxyserver, a registration request for a receiver device for accessing asecure resource; registering, at the proxy server, the receiver devicein response to the registration request; receiving, at the proxy serverand from a transmitter device different from the receiver device,information identifying the transmitter device along with authenticationcredentials for authenticating the receiver device to access the secureresource, wherein the information identifying the transmitter deviceincludes a Mobile Directory Number (MDN) and wherein the transmitterdevice and the receiver device are end-user computing devices;identifying, at the proxy server, the receiver device based at least inpart on the information identifying the transmitter device; andforwarding, from the proxy server to the receiver device, theauthentication credentials for authenticating access of the receiverdevice to the secure resource.
 2. The method of claim 1, wherein:receiving the registration request includes receiving, at the proxyserver, the registration request from the receiver device, theregistration request including location information of the receiverdevice, receiving the information identifying the transmitter deviceincludes receiving, at the proxy server, information identifyinglocation information of the transmitter device, and identifying thereceiver device includes identifying, at the proxy server, a receiverdevice from among a plurality of receiver devices being registered atthe proxy server, based on a distance between the location informationof the receiver device and the location information of the transmitterdevice being less than a predetermined threshold distance.
 3. The methodof claim 2, wherein: the secure resource include a web-based resource,the authentication credentials include credentials for accessing theweb-based resource, the transmitter device includes a mobile device of auser, and the receiver device includes a proximate computing device notpreviously associated with the user, the receiver device running a webbrowser for accessing the web-based resource.
 4. The method of claim 1,wherein: receiving, at the proxy server, the registration requestincludes receiving, at the proxy server, the registration requestincluding information identifying the receiver device and informationidentifying the transmitter device, and identifying, at the proxyserver, the receiver device includes identifying, at the proxy server, areceiver device from among a plurality of receiver devices beingregistered at the proxy server with the information identifying thetransmitter device.
 5. The method of claim 1, wherein: the secureresource includes a secure web-based resource, and the transmitterdevice includes a mobile phone of a user configured to store a pluralityof credentials for accessing a plurality of web-based resources, theplurality of credentials being associated with the user.
 6. The methodof claim 1, wherein identifying the receiver device based on theinformation identifying the transmitter device further includes:transmitting, from the proxy server and to the receiver device, averification code; and receiving, from the transmitter device and at theproxy server, a user input corresponding to the verification code. 7.The method of claim 1, wherein identifying the receiver device based onthe information identifying the transmitter device further includes:transmitting, from the proxy server and to the transmitter device, averification code; and receiving, from the receiver device and at theproxy server, a user input corresponding to the verification code. 8.The method of claim 1, wherein identifying the receiver device includesidentifying the receiver device based on a stored pairing of thetransmitter device and the receiver device.
 9. The method of claim 1,wherein identifying the receiver device includes identifying thereceiver device based on geographic location information of thetransmitter device and geographic location information of the receiverdevice.
 10. A method, comprising: receiving, at a proxy server, aregistration request for a receiver device for accessing a secureresource; registering, at the proxy server, the receiver device inresponse to the registration request; receiving, at the proxy server andfrom a transmitter device different from the receiver device,information identifying the transmitter device along with authenticationcredentials for authenticating the receiver device to access the secureresource, wherein the transmitter device and the receiver device areend-user computing devices; identifying, at the proxy server, thereceiver device based at least in part on the information identifyingthe transmitter device; and forwarding, from the proxy server to thereceiver device, the authentication credentials for authenticatingaccess of the receiver device to the secure resource, whereinidentifying the receiver device based on the information identifying thetransmitter device further includes: receiving, from the transmitterdevice, a geographic location of the transmitter device; receiving, fromthe receiver device, a geographic location of the receiver device;determining whether the receiver device is an only receiver devicewithin a specified distance from the transmitter device; upondetermining that the receiver device is the only receiver device withinthe specified distance from the transmitter device, identifying thereceiver device as a pair of the transmitter device; and upondetermining multiple receiver devices within a specified distance fromthe transmitter device, identifying the receiver device furtherincludes: transmitting, to the transmitter device, a verification code;receiving, from one of the receiver devices from among the multiplereceiver devices, a user input corresponding to the verification code;and identifying the one of the receiver devices as the receiver device.11. A method, comprising: receiving, at a proxy server, a registrationrequest for a receiver device for accessing a secure resource;registering, at the proxy server, the receiver device in response to theregistration request; receiving, at the proxy server and from atransmitter device different from the receiver device, informationidentifying the transmitter device along with authentication credentialsfor authenticating the receiver device to access the secure resource,wherein the transmitter device and the receiver device are end-usercomputing devices; identifying, at the proxy server, the receiver devicebased at least in part on the information identifying the transmitterdevice; and forwarding, from the proxy server to the receiver device,the authentication credentials for authenticating access of the receiverdevice to the secure resource, wherein identifying the receiver devicebased on the information identifying the transmitter device furtherincludes: receiving, from the transmitter device, a geographic locationof the transmitter device; receiving, from the receiver device, ageographic location of the receiver device; determining whether thereceiver device is an only receiver device within a specified distancefrom the transmitter device; upon determining that the receiver deviceis the only receiver device within the specified distance from thetransmitter device, identifying the receiver device as a pair of thetransmitter device; and upon determining multiple receiver devices thatare end-user computing devices are within a specified distance from thetransmitter device, identifying the receiver device further includes:transmitting, to each of the multiple receiver devices, a verificationcode uniquely associated with a corresponding one of the multiplereceiver devices; receiving, from the transmitter device, a user inputcorresponding a verification code corresponding to a specific one of themultiple receiver devices; and identifying the specific one of themultiple receiver devices as the receiver device.
 12. A non-transitorycomputer-readable medium comprising instructions which, when executed bya proxy server, cause the proxy server to: receive, at the proxy server,a registration request for a receiver device for accessing a secureresource; register, at the proxy server, the receiver device in responseto the registration request; receive, at the proxy server and from atransmitter device different from the receiver device, informationidentifying the transmitter device along with authentication credentialsfor authenticating the receiver device to access the secure resource,wherein the information identifying the transmitter device includes aMobile Directory Number (MDN) and wherein the transmitter device and thereceiver device are end-user computing devices; identify, at the proxyserver, the receiver device based at least in part on the informationidentifying the transmitter device; and forward, from the proxy serverto the receiver device, the authentication credentials forauthenticating access of the receiver device to the secure resource. 13.The non-transitory computer-readable medium of claim 12, wherein: theinstructions to receive the registration request include instructions toreceive, at the proxy server, the registration request from the receiverdevice, the registration request including location information of thereceiver device, the instructions to receive the information identifyingthe transmitter device include instructions to receive, at the proxyserver, information identifying location information of the transmitterdevice, and the instructions to identify the receiver device includeinstructions to identify, at the proxy server, a receiver device fromamong a plurality of receiver devices being registered at the proxyserver, based on a distance between the location information of thereceiver device and the location information of the transmitter devicebeing less than a predetermined threshold distance.
 14. Thenon-transitory computer-readable medium of claim 13, wherein: the secureresource include a web-based resource, the authentication credentialsinclude credentials for accessing the web-based resource, thetransmitter device includes a mobile device of a user, and the receiverdevice includes a proximate computing device not previously associatedwith the user, the receiver device running a web browser for accessingthe web-based resource.
 15. The non-transitory computer-readable mediumof claim 13, wherein: the secure resource includes a secure web-basedresource, and the transmitter device includes a mobile phone of a userconfigured to store a plurality of credentials for accessing a pluralityof web-based resources, the plurality of credentials being associatedwith the user.
 16. The non-transitory computer-readable medium of claim12, wherein: the instructions to receive, at the proxy server, theregistration request include instructions to receive, at the proxyserver, the registration request including information identifying thereceiver device and information identifying the transmitter device, andthe instructions to identify, at the proxy server, the receiver deviceinclude instructions to identify, at the proxy server, a receiver devicefrom among a plurality of receiver devices being registered at the proxyserver with the information identifying the transmitter device.
 17. Thenon-transitory computer-readable medium of claim 12, wherein theinstructions to identify the receiver device based on the informationidentifying the transmitter device further include instructions to:transmit, from the proxy server and to the receiver device, averification code; and receive, from the transmitter device and at theproxy server, a user input corresponding to the verification code.
 18. Asystem comprising: one or more processors; and a memory comprisinginstructions which, when executed by the one or more processors, causethe one or more processors to: receive, at a proxy server, aregistration request for a receiver device for accessing a secureresource; register, at the proxy server, the receiver device in responseto the registration request; receive, at the proxy server and from atransmitter device different from the receiver device, informationidentifying the transmitter device along with authentication credentialsfor authenticating the receiver device to access the secure resource,wherein the information identifying the transmitter device includes aMobile Directory Number (MDN) and wherein the transmitter device and thereceiver device are end-user computing devices; identify, at the proxyserver, the receiver device based at least in part on the informationidentifying the transmitter device; and forward, from the proxy serverto the receiver device, the authentication credentials forauthenticating access of the receiver device to the secure resource.